Skip to main content

PUT Geoblocking Rule for Live Video

Overview


The table below provides key details about the PUT method for uploading geoblocking rules for a specific live video.

PUT Geoblocking Rule for Live Video
MethodPUT
URL or Endpoint/api/v1/projectId/live-videos/geo-blocking- rules
HeadersAuthorization
Content Typeapplication/json
ParametersprojectId
BodyvideoId, geoblockingRuleId

The description of the URL parameter is as follows:

projectId URL Parameter
URL Parameter NameprojectId
MandatoryYes
Typestring
DescriptionUnique Id of the project.

Request Body

{
"videoId": "string",
"geoBlockingRuleId": 0
}

The description of the body parameters is as follows:

Parameter NameMandatoryTypeDescription
videoIdYesstringPublic identifier of the live video
geoBlockingRuleIdYesinteger($int32)Unique identifier of specific rule

Response

{
"success": true,
"errors": [],
"messages": [],
"result": true,
"resultInfo": null,
"statusCode": 200
}

Information about the fields that appear when you receive the response are displayed in the table below.

Field NameTypeDescription
successboolIf the response is successful it will return true. Otherwise will return false.
errorsarray[]Indicates if there was an error.
messagesarray[]Returns the response message from back-end.
resultboolReturns a boolean value indicating the success or failure of the request.
resultInfostringReturns extra information about the result.
statusCodeinteger($int32)Returns the HTTP Status Code.

If the action is successful, the service sends back an HTTP 200 or 201 response.

Errors

For information about the errors that are common to all actions, see Common Errors:

  • HTTP Status Code 400: Bad Request

  • HTTP Status Code 401: Unauthorized

  • HTTP Status Code 403: Forbidden

  • HTTP Status Code 404: Result Not Found

  • HTTP Status Code 500: Internal Server Error

  • HTTP Status Code 503: Backend Fetch Failed